View CDK2000-CLK_1041069.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

copyright ? cirrus logic, inc. 2008 (all rights reserved) http://www.cirrus.com cdk2000 clocking device development platform features ? modular design ? motherboard/daughter card design allows flexible use and evaluation of all members of the cs2000 device family ? software and hardware control ? usb connector for use with cdk2000 configuration wizard windows ? pc-based software ? dip switches for st and-alone control in hardware mode ? dual clock inputs ? industry standard bnc connectors for ref_clk and clk_in with input buffers ? dual clock outputs ? industry standard bnc connectors for clk_out and aux_out with output buffers ? usb powered ? evaluation platform is entirely usb-powered; no separate power supply necessary ? onboard boost converter generates programming voltage description the cdk2000 ia a flexible modular development plat- form designed to allow evaluation of all members of the cs2000 clocking device family, including all members of the cs2000, cs2100, cs2200, and cs2300 device sub-families. for one-time programmable (otp) parts, the cdk2000 platform also allows for the development, test, and production programming of custom device configurations. the on-board firmware handles all aspects of program- ming the dut and transitioning it between modes. furthermore, the cdk2000 configuration wizard soft- ware is available for real-time control of duts that can run in control port mode. cs2000 family device clk_out aux_out power supply usb c dip switches hw/sw mode control ref_clk clk_in osc cdk2000 april '08 ds821db1
cdk2000 2 ds821db1 table of contents 1. development platform overview ........................................................................................... 4 1.1 hardware components ....................................................................................................... ............. 4 1.2 software components ...... ................................................................................................. .............. 5 2. quick-start guide .......................................................................................................... ................. 8 2.1 software installation ..................................................................................................... .................... 8 2.2 control port device evalua tion ............................................................................................ ............ 8 2.3 one-time-progra mmable device evaluation and programming ..................................................... 8 2.3.1 device evaluation ....................................................................................................... ............. 8 2.3.2 device programming - development mode ............................................................................ 9 2.3.3 device programming - production mode .............................................................................. 10 3. hardware system overview ................................................................................................... .. 10 3.1 power supply .............................................................................................................. ................... 10 3.2 daughter card interface headers ........................................................................................... ....... 10 3.3 clock inputs .............................................................................................................. ..................... 11 3.4 clock outputs ............................................................................................................. ................... 11 3.5 micro-controller .......................................................................................................... ................... 11 3.6 dut software mode control ....................... .......................................................................... ......... 12 3.7 hardware mode control ..................................................................................................... ............ 12 4. hardware usage and operation ............................................................................................ 12 4.1 general considerations .................................................................................................... ............. 12 4.1.1 power supply ............................................................................................................ ............ 12 4.1.2 input and output clocks ................................................................................................. ....... 12 4.1.3 push-button operation ................................................................................................... ....... 13 4.2 pre-programmed devices .................................................................................................... .......... 13 4.3 control port devices (-cp) ................................................................................................ ............ 13 4.4 one-time programmable devices (-otp) ..................................................................................... 1 3 4.4.1 programming -otp devices ....................... ......................................................................... .13 4.4.2 development and production modes .......... .......................................................................... 13 4.4.3 program sequence executio n and result codes ................................................................. 14 4.4.4 result code details ..................................................................................................... .......... 15 5. user interface elements overview ...................................................................................... 16 6. cdb2000-mb schematics and layout ...................................................................................... 17 7. cdb2000-dc schematics and layout ....................................................................................... 22 8. cdb2000-pc schematics and layout ....................................................................................... 24 9. ordering information ....................................................................................................... ......... 26 10. revision history .......................................................................................................... ................ 26
cdk2000 ds821db1 3 list of figures figure 1.cs2000 family conf iguration wizard, cs2000-cp device selected in demo mode .................. 5 figure 2.calculator tool ...................................................................................................... ........................ 6 figure 3.cs2000 family conf iguration wizard, cs 2000-otp device selected in demo mode ................ 6 figure 4.cs2000 family conf iguration wizard, cs 2000-otp device selected in form entry mode ........ 7 figure 5.cdb2000-mb schematic page 1 .......................................................................................... ...... 17 figure 6.cdb2000-mb schematic page 2 .......................................................................................... ...... 18 figure 7.cdb2000-mb component map ............................................................................................. ..... 19 figure 8.cdb2000-mb top layer ................................................................................................. ............ 19 figure 9.cdb2000-mb inner layer 1 - ground .................................................................................... .... 20 figure 10.cdb2000-mb inner layer 2 - power .................................................................................... .... 20 figure 11.cdb2000-mb bottom layer ............................................................................................. ........ 21 figure 12.cdb2000-dc schematics ............................................................................................... ......... 22 figure 13.cdb2000-dc component map ............................................................................................ .... 22 figure 14.cdb2000-dc top layer ................................................................................................ ........... 23 figure 15.cdb2000-dc inner layer 1 - ground ................................................................................... .... 23 figure 16.cdb2000-dc inner layer 2 - power .................................................................................... .... 23 figure 17.cdb2000-dc bottom layer ............................................................................................. ......... 23 figure 18.cdb2000-pc schematics ............................................................................................... .......... 24 figure 19.cdb2000-pc component map ............................................................................................ ..... 24 figure 20.cdb2000-pc top layer ................................................................................................ ........... 25 figure 21.cdb2000-pc inner layer 1 - ground ................................................................................... .... 25 figure 22.cdb2000-pc inner layer 2 - power .................................................................................... ..... 25 figure 23.cdb2000-pc bottom layer ............................................................................................. ......... 25 list of tables table 1. cdb2000-pc family daughter cards ..................................................................................... ..... 4 table 2. cdb2000-dc family daughter cards ........ ............................................................................. ..... 4 table 3. error codes .......................................................................................................... ....................... 14 table 4. user interface elemen ts .............................................................................................. ................ 16 table 5. dip switch positions ................................................................................................. ................... 16
cdk2000 4 ds821db1 1. development platform overview 1.1 hardware components the cdk2000 clocking device development platform hard ware components consist of a motherboard and a number of individual daughter cards that, when connected, make a complete development system. the cdb2000-mb is the motherboard of the developme nt system. this board houses all clock i/o connec- tors, control switches, power supplie s, and pc interface hardware. two single-row sockets are provided for connections to any of the availa ble daughter cards. the motherboard facilitates pc assisted development and evaluation, as well as stand-alone production enviro nment programming capabilities. the cdb2000-pc represents a family of socketed daughter cards for use with the cdb2000-mb mother- board. each daughter card features an open-top push-down socket to quickly insert and remove duts at will, and is suitable for programming and testing multip le duts in a production environment. the cdb2000- pc family daughter cards are capable of supporting both control port and one-time-programmable devices. two population options are available, each designed to support a specific frequency reference source for the dut. the cdb2000-pc-clk can be easily modified to support an on-card crystal as the ref_clk source. a few population changes are all that is required. see the cdb2000-pc schematics in figure 18 on page 24 for population change details. the cdb2000-dc represents a family of soldered-down device daughter cards for use with the cdb2000- mb. each daughter card features a soldered-down du t for optimal performance and is most suitable for prototyping and performance evaluation. the cdb2000-dc family daughter cards are capable of support- ing both control port and one-time-programmable devi ces. two population options are available, each with a specific cs2000 family device soldered-down, and each designed to support a specific frequency refer- ence source for the dut. the cdb2000-dc-clk can be easily modified to support an on-card crystal or oscillator as the ref_clk source. a few population changes are all that is required. see the cdb2000-dc schematics in figure 12 on page 22 for population change details. the complete ordering number of a cdb2000-dc daughter card will indica te the specific device soldered- down by substituting the soldered-d own device number in place of ?200 0? and appending either ?-cp? for control port device, or ?-otp? for a one-time prog rammable device. for example, a cdb2000-dc-clk with a cs2100-cp soldered-down would be ordered as cdb2100-dc-clk-cp. development kits best suited for evalua tion of particular sub-fa mily devices are availabl e; each contains one motherboard and various combinations of th e most appropriate daughter cards. see ?ordering information? on page 26 for complete details of the available kits. daughter card frequency reference source sub-family devices supported cdb2000-pc-clk oscillator or bnc connecto r on motherboard. cs200 0, cs2100, cs2200 cdb2300-pc-lco internal lc oscillator. cs2300 table 1. cdb2000-pc family daughter cards daughter card frequency reference source sub-family devices supported cdb2000-dc-clk oscillator or bnc connector on motherbo ard. cs2000, cs2100, cs2200 cdb2300-dc-lco internal lc oscillator. cs2300 table 2. cdb2000-dc family daughter cards
cdk2000 ds821db1 5 1.2 software components the cdk2000 software tools, known as ?configuration wizard?, facilitate the virtual configuration and hard- ware control of any cs2000 family device, including all devices in th e cs2100, cs2200, and cs2300 sub- families. the cs2000 family configuration wi zard is available for download from the cs2000 family product pages on http://www.cirrus.com . this software tool presents an intuitive user interface to all configuration options of the cs2000 family devices. the software offers two modes of operation: demo mode and live mode. the wizard will start up in demonstrat ion (demo) mode regardless of the presence of usb connection to a cdk2000 (noted by the text ?cs2000 wizard is running in demo mode? in the bottom left and ?discon- nected? in the menu bar). in demo mode the differen t devices in the cs2000 family may be selected from the ?device select? menu. once the desired device is selected, changes can be made to the gui which cor- respond to the selectable configuration options of the selected device. demo mode is exited by selecting ?connect to cdk2000? from the ?cdk controls? menu. a screen capture of the configuration wizard in demo mode is shown below. figure 1. cs2000 family configuration wiza rd, cs2000-cp device se lected in demo mode
cdk2000 6 ds821db1 the wizard offers a calculator tool located in ?tools -> calculator?. this allows easily calculation of ratio values based off of desired input and output frequencie s. the calculator can be re-configured to solve for output or input frequency when given a specific ratio us ing the radio buttons at the left. a screen capture of the calculator is shown below. the interface for a one-time-programmable device is slightly different. the maroon/dark red drop down menus correspond to the modal configuration parameters (see the cs2x00-otp datasheet for details). the ?mode select? drop down at the top allows simulation of the m1:0 pins as well as configuration of the 4 modal configuration sets. the m2 low/high button simulates the usage of the m2 pin. the bright red drop down selects the m2 global config paramet er and the associated control will be ou tlined in red. a screen capture of the configuration wizard configured for -otp is shown below. figure 2. calculator tool figure 3. cs2000 family configuration wizard, cs2000-otp device selected in demo mode
cdk2000 ds821db1 7 alternately the form entry mode can be used to evaluate the -otp when referencing the form found in the cs2x00-otp family datasheet. this also allows the view of all 4 modal configuration sets at once for quicker setup and for verification of settings. a screen captur e of the configuration wizard configured for -otp is shown below. figure 4. cs2000 family configuration wizard, cs2000-otp device selected in form entry mode
cdk2000 8 ds821db1 2. quick-start guide 2.1 software installation iinstalling the cs2000 family configuration wizard software 1. browse to http://www.cirrus.com and navigate to a cs2000 family product page. 2. click the ?cs2000 family configur ation wizard? link unde r the ?tools and softw are? headin g. a page containing the software licens ing agreement will be loaded. 3. click ?agree? to begin the download proc ess. allow the download to complete. 4. unzip the package and launch the insta ller to begin the installation process. 5. click ?finish? to complete the installation process. 2.2 control port d evice evaluation 1. connect a cdb2000-dc or cdb2000-pc family board to a cdb2000-mb. 2. ensure that an appropriate cs2000 family contro l port (-cp) device is so ldered to the cdb2000-dc family board, or insert an appropriate cs2000 family control port (-cp) device into the socket on the cdb2000-pc family board. 3. connect your pc?s usb port to the cdb2000-mb. 4. launch the cs2000 family configuration wizard. 5. using the ?cdk controls? menu, select ?connect to cdk2000?. 6. click ?yes? to establish a connec tion with the board; th en press ?ok? on the usbxpress success mes- sage. 7. if the device in the socket do es not match the current gui config uration you will get the ?warning! de- vice mismatch!? message. click ?yes? to allow the gui to configure itself according to the device found on the cdk2000. if this is not th e device you intended to evaluate then click ?no? which powers down the device and you may then change the daughter card to the appropriate device. 8. use the graphical user interface to define the devi ce?s operation. alternatively, choose ?file -> load configuration? to load a pre-configured device configuration. 9. registers may be manipulated using the ?read regi ster? and ?write register? buttons in the bottom right of the window. 10. to power-off the evaluation platform, simply clos e the wizard application and remove the usb cable from the cdb2000-mb. 2.3 one-time-programmable devi ce evaluation and programming otp devices are shipped from the factory un-program med. the device settings can be evaluated prior to programming by the use of preview mode (see ?programming -otp devices? on page 13 ). once evaluated, the devices can be programmed with the cdk in one of two modes: development and production. devel- opment mode provides a variety of debugging options, while production mode allows for faster program- ming cycle times. see ?development and production modes? on page 13 for more information. 2.3.1 device evaluation 1. connect a cdb2000-dc or cdb2000-pc family board to a cdb2000-mb. 2. ensure that an appropriate cs2000 family one-ti me-programmable (-otp) device is soldered to the cdb2000-dc family board, or insert an appropriate cs2000 family one-time-programmable (-otp) device into the socket on the cdb2000-pc family board. 3. connect your pc?s usb port to the cdb2000-mb.
cdk2000 ds821db1 9 4. launch the cs2000 family configuration wizard. 5. using the ?cdk controls? menu, select ?connect to cdk2000?. 6. click ?yes? to establish a conn ection with the board; then press ?ok? on t he usbxpress success message. 7. if the device in the socket does not match the current gui configuration you will get the ?warning! device mismatch!? message. click ?yes? to allow the gui to configur e itself according to the device on the cdk2000. if this is not the device you intend ed to evaluate then click ?no? which powers down the device and you may then change the daughter card to the appropriate device. 8. use the graphical user interface to define the device ?s operation. alternatively, choose ?file -> load configuration? to load a pre-configured device configuration. note: the settings will not yet be programmed into the one-time-pro grammable memory. the wizard presents the user with a graphical controls over an internal virtual representation of the m2, m1, and m0 pins. the purpose of these controls is to facilitate th e evaluation of the device?s currently previewed configuration. these gra phical controls can be toggled, and the device will respond exactly as it will once the configuration is programmed into one-time-progr ammable memory and the m2, m1, and m0 pins are toggled. 9. evaluate the current configuration by toggling the state of the ?mode select? drop down and by pressing the m2 low/high button, checking the device?s functionality for the desired response. 10. repeat steps 8 - 9 until the desired configuration is achieved. 11. once the desired configuration is achieved select ?cdk controls -> write preview data to mcu...? from the wizard to save the current configurat ion to memory within the microcontroller on the cdb2000-mb this step downloads the current configuration into fl ash memory within the microcontroller. once this step is complete, a one-time-programmable memory programming sequence can be initiated by either software control through the wizard or hardware control through a push-button on the cdb2000-mb. 2.3.2 device programming - development mode 12. to program the one-time-programmable memory in the cs2000 family device using the wizard software, select ?cdk controls -> initiate otp sequence...?. 13. to program the one-time-programmable memory in the cs2000 family device using the hardware controls on the cdb2000-mb a) close the wizard software. the following steps reference the cdb2000-mb hardware. b) verify that d9 is lit, indicating that th e cs2000 family device is in hardware mode. c) place dip switch position 5 into the upper (or opened) position to select development mode. d) press and hold the on-board push-button (s1) for more than 1 second to program the otp memory. 14. after the programming sequence is complete, the cs2000 family de vice will be able to operate in hardware mode as defined by the programmed configuration. simply ensure that the cdk2000 configuration wizard application is closed, and verify that d9 is lit indicating that the cs2000 family device is in hardware mode. the m2, m1, and m0 switches on the cdb2000-mb will control its operation. 15. to power-off the evaluation platform, ensure that the cdk2000 configuration wizard application is closed and remove the usb cable from the cdb2000-mb.
cdk2000 10 ds821db1 2.3.3 device programming - production mode 12. to program the one-time-programmable memory in the cs2000 family device using the wizard software, select ?cdk controls -> initiate otp sequence...?. 13. to program the one-time-programmable memory in the cs2000 family device using the hardware controls on the cdb2000-mb a) close the wizard software. the following steps reference the cdb2000-mb hardware. b) verify that d9 is lit, indicating that th e cs2000 family device is in hardware mode. c) place dip switch position 5 into the lower (or closed) position to select production mode. d) press and hold the on-board push-button (s1) for more than 1 second to program the otp memory. 14. after the programming sequence is complete, the cs2000 family device will be powered down (indicated by d3 ?vdut? led off) so that the device can be removed from the socket and the next blank part can be inserted. 15. insert the next blank part into the socket. 16. briefly press the push button s1 to power up the device 17. repeat steps 13 d - 16 (of section 2.3.3 ) until the desired number of parts are programmed. 3. hardware system overview 3.1 power supply the entire cdk2000 platform is powered via the usb connector from a self-powered usb hub, which pro- vides a voltage between 4.75 and 5.25 v. other usb comp liant power supplies, such as an ac (wall) adapt- er or a dc (car) adapter, may be used as well. whenev er a suitable usb power su pply is connected, d13 will be lit to indicate such. a fixed voltage regulator (u10) provides the 3.3 v supp ly for the micro-controller, status leds, and three of the four clock buffers. an integrated zetex? boost converter, consisting of a controller (u9) and a rectifier (u8), generates an in- termediate 7.2 v supply that feeds into an adjustable lin ear regulator (u5). the feedback network of the lin- ear regulator is designed such that u5 generates either 3.3 v (with q3 in the ?on? state) or 6.5 v (with q3 in the ?off? state). this supply powers the dut and the fourth clock buffer (u3). the selection between the two output voltages is made via the vdut.prog.en signal generated by the micr o-controller. d4 is lit when the higher (programming) voltage is applied to the dut. furthermore, the adjustable linear regulator may be shut down in order to cut off the power supply to the dut when vdut.en is low (via inverter u4-c). q2, in conjunct ion with r34, discharges the bulk decoupling cap (c14) when the supply is powered down. the powe r-up/down state of u5 is controlled via the vdut.en signal generated by the micro-controller. d3 indica tes whether power is currently supplied to the dut. d11 indicates an error condition (overload) of the boos t controller. in order to prevent damage to the boost converter, the usb supply should be removed immedi ately when such an error occurs. check the board and connectors for shorts before proceeding. 3.2 daughter card interface headers the cs2000 family device must be attached to the mo therboard via one of the daughter cards described in section 1 on page 4 . the desired daughter card plugs into the receptacles j1 and j8 on the motherboard. make sure to align the large white triangle on the da ughter card with the corresponding triangle on the moth- erboard before inserting to ensure proper orientation.
cdk2000 ds821db1 11 a header (j2) is provided for current measurements. fo r normal operation, r1 is shorted by a shunt on j2. if the shunt is removed, the current passes through r1 and a volt meter may be attached to j2. the current consumed by the cs2000 family device is proportional to the voltage that drops over r1 and can be easily calculated by dividing the voltage measur ed on j2 by the resistance of r1 (1 ? ). 3.3 clock inputs the dut (depending on the particular variant used) r equires up to two clock inputs, ref_clk and clk_in. note that the ref_clk and clk_in bnc inputs are terminated with 50 ohms by r23 and r14. the cs2000, cs2100, and cs2200 sub-family devices require an external ref_clk to be supplied and can all be used with either the -xtl, -osc, or -c lk daughter cards. the cs2300 sub-family generates ref_clk internally and must be used with an -lco daughter card. there are several options to generate ref_clk (see table 1 and table 2 on page 4 ). if a -xtl or -osc daughter card is used, ref_ clk is generated on the da ughter card by a local crystal or a local oscillator, respectively. if a -clk daughter card is used, ref_clk will be su pplied from the mo therboard via the header (j8). on the motherboard, there are two possible sources for re f_clk, the right-angled bnc connector (j6) or the on-board oscillator (y1) . the selection between the two is made via dip switch position 1, which generates the osc.refclk.en signal. u2-c is used as an inverter for osc.refclk.en and generates the bnc.refclk.en signal. if the switch is in the lo wer (closed) position, osc.refclk.en is pulled low and powers up the oscillator via q1. it also enables the tri-statable buffer u3-c to pass the oscillator output to the dut. if the switch is in the up per (open) position, osc.refclk.en is pulled high (via r61), which pow- ers down the oscillator and tr i-states u3-c. bnc.refclk.en is then low, which enables the tri-statable buffer u3-b to pass the bnc input from j6 to the dut . d1 and d2 visually indicate which ref_clk source is currently selected via the dip switch. clk_in is always routed from the bnc connector (j 3) to the dut via a buffer (u2-b) and header j1. clk_in is required for the cs2100 and the cs2300 sub-familie s. it is optional fo r the cs2000 sub-family and not supported on the cs2200 sub-family. if it is not desirable to buffer the input clocks to the dut, u2-b may be bypassed by moving the 22 ? resistor from position r6 to position r5. likewise, u3-b may be bypassed by moving the 22 ? resistor from position r26 to position r25. 3.4 clock outputs the dut supports two outputs, clk_out and aux_out. clk_out is routed from the dut to the output buffer u4-b via header j1 and on to the bnc connector j7. aux_out is routed from the dut to the output buffer u1-b via header j1 and on to the bnc connector j4. if it is not desirable to buffer the output clocks from the dut, u4-b may be bypassed by moving the 22 ? resistor from position r30 to position r27. likewise, u1-b may be bypassed by moving the 22 ? resistor from position r8 to position r9. u4-c and u1-c are used to invert miscellaneous contro l signals that are needed by other functional blocks. 3.5 micro-controller the cdb2000-mb utilizes a silabs ? 8051-compatible micro-controller with integrated usb phy for con- venient interconnect to a pc. the micro-controller co mes pre-programmed with custom firmware that allows it to interact with the cdk2000 configuration wizard as well as operate in stand-alone mode without a pc.
cdk2000 12 ds821db1 if the cdb2000-mb platform is connected to a pc via usb and the cdk2000 configuration wizard host software has established co mmunications with the board, d8 will be lit to indicate micro-controller software mode. (note that micro-controller software mode doesn 't mean the dut operates in software mode, which is entirely independent. it just means that the mi cro-controller is communicating with the cdk2000 config- uration wizard software on a pc.) the micro-controller interfaces with other blocks on the board via various logic signals. it receives input from push-button s1 and dip switch positions 5 and 6. it also generates various control and status signals. vdut.prog.en and vdut.en control the power supply to the dut. dut.prog.run , dut.prog.succ , and dut.prog.fail indicate various status and error conditions via led d5/6/7. dut.hw/sw controls the board-level logic to corres pond with the operational mode of the dut. 3.6 dut software mode control in software mode, the dut communicates with the micro-controller via i2c ? . the i2c clock and data lines are routed through q5/q7 and q8/q4, respec tively, which are all ?on? when dut.sw/hw is high (via invert- er u1-c). d10 is lit to indicate that the dut is in software mode. (note that dut software mode is indepen- dent of micro-controller software or hardware mode. the dut automatically enters software mode when it detects a valid i2c transaction on its control port and must be reset to enter hardware mode. the micro- controller transitions the board-level logic between ha rdware and software modes as needed to match the dut hardware/software mode.) 3.7 hardware mode control when the dut is in hardwa re mode, its operational state is determ ined by the three mode pins (m2:0). in this case dip switch positions 2, 3, and 4 directly connect to the mode pins since q9/10/11 are ?on? due to the micro-controller driving dut.hw/sw high, and q4/5/7/8 are ?off? due to dut.sw/hw being low (via in- verter u1-c). when a dip switch is in the lower (clo sed) position, the corresponding mode pin is logic 0; when a dip switch is in the upper (open) position, the corresponding mode pin is logic 1 (via pull-up resistors r52/53/54). d9 is lit to indicate that the dut is in hardware mode. 4. hardware usage and operation 4.1 general considerations 4.1.1 power supply a usb connection is required to power the cdk2000 pla tform and the dut. if the board is to be used in software mode, it must be connected to a pc, either directly or via a self-powered hub. if board operation in software mode is not required, an alternate u sb power supply (such as a wall adapter) may be used instead. the latter is useful for duts that only operate in hardware mode or in a production environment where multiple duts are to be programmed on an asse mbly floor and a pc is not available for each work- station. 4.1.2 input and output clocks connect the desired input cloc k sources as described in section 3.3 on page 11 . if ref_clk is sourced from the motherboard (-clk daughter card option), use dip switch position 1 to toggle the ref_clk source between the bnc connector (j6) and the on- board oscillator (y1). if re f_clk is generated locally (-xtl, -osc, and -lco daughter card options), set di p switch position 1 to t he open (bnc) position and disconnect any external clock sources from j6 in order to minimize clock interferences. observe the desired clock outputs on j7 and j4 as described in section 3.4 on page 11 .
cdk2000 ds821db1 13 4.1.3 push-button operation when the board is in hardware mode (usb is powered but the software is not invoked), the on-board push-button (s1) allows for the invocation of variou s actions with the board in hardware mode. pressing s1 briefly (less than one second) will toggle v dut on and off. d3 indicates the current v dut enable status. if v dut is on, briefly pressing s1 twice in a row will re set the dut. pressing and ho lding s1 for more than a second will initiate the programming sequence (see section 4.4.1 on page 13 ), regardless of the power on/off state of the dut. if the board is operating in software mode, those action s may only be invoked via the configuration wizard software interface and the boar d will not respond to an y push-button interac- tions. 4.2 pre-programmed devices fully pre-programmed duts can only o perate in hardware mode. to utiliz e the cdk2000 platform with the dut in hardware mode, use dip switch positions 2, 3, and 4 to apply t he desired logic level to the m2:0 pins of the dut. d9 indicates that the dut is running in hardware mode. 4.3 control port devices (-cp) control port devices can only operate in software mo de. use a pc running the cdk2000 configuration wiz- ard software to adjust all functional parameters in real -time. d10 indicates that t he dut is running in soft- ware mode. 4.4 one-time programm able devices (-otp) one-time programmable devices initially (prior to pr ogramming) operate in preview mode. after program- ming, they may operate in either preview or hardware mode. to operate a device in preview mode, use a pc running the cs2000 family configuration wizard to adjust the modal and global parameters in real-time. to operate a device in hardware mode see section 4.2 on page 13 . 4.4.1 programming -otp devices in order to program a device, a configuration file must first be transferred to the micro-controller via the configuration wizard. see ?one-time-programmable device eval uation and programming? on page 8 for details on how to achieve this. once a configuration file has been uploaded to the board it is stored in flash memory and will be retained, even if power is disconnected or lost, and any numb er of duts may be pro- grammed with this configuration. it is therefore possible to develop and test the configuration file on a pc, and then transfer the cdk2000 platform into a producti on environment to program a large quantity of de- vices without requiring a pc. 4.4.2 development and production modes programming the dut may be done in either development or production mode, which are selected via dip switch position 5. the difference between the tw o is how mismatches (if any) between the content of the configuration file and the content of the pre-programmed otp in the dut will be handled. due to the architecture and design of the otp, each bit position can only be transitioned from a ?0? to a ?1?. once a ?1? has been programmed into a particular bit position, it can never be returned to a ?0?. in addition, certain bit positions will be locked at the fa ctory such that a transition from ?0? to ?1? is also prohibited. in development mode (dip switch position 5 in the upper (or open) position), if any violations occur, the programming se quence will continue and only flag a warning at the end. programming will proceed on a best-effort basis; that is, any violations are disre garded (and the affected bit positions left unchanged) while all other bit positions will be pr ogrammed as requested. this mode is most suitable for a prototyping environment when strict error enforceme nt of mismatches is not desirable.
cdk2000 14 ds821db1 in production mode (dip switch position 5 in the lower (or closed) position), if any violations occur, the programming sequence is terminated immediately (before writing to the otp on the dut) and an error condition will be flagged. th is mode is most suitable for a production environm ent where strict enforce- ment of mismatches is desired, fo r instance to detect a situation wher e a configuration file was designed for a different base part than what?s currently pres ent on the board, and thereby preventing a large batch of parts from being mis-programmed. furthermore, in development mode, at the end of the pr ogramming sequence, th e dut will be reset and remain in a powered-on state to allow for verification and continued development; whereas in production mode, at the end of the programm ing sequence the dut will be powere d-down to allow for removal from the socket and insertion of another dut. 4.4.3 program sequence e xecution and result codes after a configuration file has been downloaded and the board has been properly configured for either de- velopment or production mode, the actual programming sequence may th en be initiated via the push-but- ton (s1) or via the host software (see section 4.1.3 on page 13 for details). d5 (prog.run) will be lit while the programming sequence is in progress. during the execution of the programming sequence, d3 (v dut ), d4 (v prog ), d9 (dut.sw), and d10 (dut.hw) will turn on and off repeatedl y as the micro-con- troller goes through the various steps necessary to program the device. at the end of the programming sequence, d5 (prog.run), d6 (p rog.success), and d7 (prog.fail) will indicate one of several possible result codes as outlined in table 3 below. table 3. error codes the led pattern for each result code has been carefully designed to convey as much information as pos- sible without being confusing or overwh elming. in all cases, at most one of the three leds will be lit in a solid on state: ? if the yellow run led is lit solid, program ming is in progre ss, pending results. ? if the green succ led is lit solid, the programmi ng sequence concluded without errors. the other two status leds indicate warnings, if any. error code result/status d5 (run) d6 (succ) d7 (fail) 0 programming in progress on off off 1 success: no erro r encountered off on off 2 warning: attempt to clear a ?1? in otp off on flash 3 warning: attempt to set a locked ?0? in otp flash on off 4 warning: attempt to clear a ?1 ? and set a locked ?0? in otp flash on flash 5 invalid: no configuration file present flash flash flash 6 invalid: no dut found off off flash 7 invalid: dut is not a member of the cs2000 family flash off flash 8 invalid: unsupported revision of cs2000 family device off flash flash 9 error: register read error flash flash on 10 error: attempt to clear a ?1? in otp off flash on 11 error: attempt to se t a locked ?0? in otp flash off on 12 error: attempt to clear a ?1? and set a locked ?0? in otp flash flash on 13 error: otp read-back error off off on 14 error: general or unknown error flash flash on
cdk2000 ds821db1 15 ? if the red fail led is lit solid, the programming sequence concluded with one or more errors. the oth- er two status leds indicate the nature of the error(s). ? if no led is lit solid and the red fail led is flas hing, the micro-controller encountered an invalid con- dition that must be corrected before proceeding. great care has been taken to choose very simple led patterns for those result codes that are exceedingly likely to occur in a production environment, that is resu lt codes 0, 1, and 13. all three of these results are indicated by a single lit led with the other two status leds in the off state. this way, a production floor operator can quickly glance at the board and immediately classify the resu lt as wait, fail, or pass. the other error codes are either limited to development mode, setup errors (which would be caught prior to an operator taking over), or are rather unlikely to occur. 4.4.4 result code details ? 0 (programming in progress) - this result code really means that programming is not finished, and no result is available quite yet. the board should only re main in this state for a few seconds. if this condi- tion persists for more than 20 seconds, the mi cro-controller should be reset via push-button s2. ? 1 (success: no error) - the dut was programmed successfully and no errors were encountered. ? 2/3/4 (warning: otp conf iguration violation) - development mode only - one or more otp con- figuration violations were encountered, but progra mming continued on a best-effort basis. the offend- ing bit positions were left unchanged, while all others were programmed as desired. ? 5 (invalid: no configuration file found) - the micro- controller has not received a valid configuration file. refer to the software documentation and upload a valid configuration file to the board before proceed- ing. ? 6 (invalid: no dut found) - the micro-controller was unable to find a dut on the board. this means either no dut is present, or the dut is defective. replace the dut before proceeding. ? 7 (invalid: dut is not a cs2000 family device) - a dut was found on the board, but it doesn?t appear to be a cs2000 family device. the cdk2000 platform only supports cs2000 family devices. replace the dut before proceeding. ? 8 (invalid: unsupported revision) - the revision of the cs2000 family device found is not supported. the firmware can only program cs2000 family devices of revision b2 or above. revisions b1 and be- low are not supported. replace the dut before proceeding. ? 9 (error: register read error) - the firmware encounte red a register read error. most likely, this indicates a defective dut. you may try to invoke the programming sequence again. if the error persists, replace the dut before proceeding. ? 10/11/12 (error: otp configurat ion violation) - production mode only - one or more otp con- figuration violations were encountered, and the du t was not programmed. this error indicates either an invalid configuration file or a configuration file that doesn?t match the du t variant currently present on the board. make sure the configuration file was created for the proper target dut, and verify the correct dut variant is present. ? 13 (error: otp read-back error) - the dut was programmed, but otp read-back verification failed. this error indicates a defective dut that must be replaced. ? 14 (error: general or unknown error) - a miscellane ous error occurred. this could indicate a defective dut or a problem with the board hardware or the micro-controller firmware. you may wish to try again, first with the same and th en with a differ ent dut. if the error still persists, a hardware problem is pos- sible.
cdk2000 16 ds821db1 5. user interface elements overview table 4 below serves as a quick reference to all user interface elements and table 5 outlines the various dip switch position. table 4. user interface elements table 5. dip switch positions reference designator silkscreen label description d1 bnc ref_clk source set to bnc connector d2 osc ref_clk source set to on-board oscillator d3 vdut dut is powered up d4 vprog dut supply set to high (programming) voltage d5 prog.run programming sequence in progress (see section 4.4.3 on page 14 for details) d6 prog.succ programming sequence successful (see section 4.4.3 on page 14 for details) d7 prog.fail programming sequence failed (see section 4.4.3 on page 14 for details) d8 micro.sw micro-controller is operating in software mode d9 dut.hw dut is operating in hardware mode d10 dut.sw dut is operating in software (control port or preview) mode d11 eor boost converter overload - unplug usb power s upply immediately! d13 usb board is connect ed to usb power supply j1/j8 - daughter card receptacles j2 idut place shunt or measure voltage to determine dut supply current j3 clk_in clk_in input for cs2000, cs2100, and cs2300 sub-family devices j4 clk_out clk_out output j5 - input for external control signals (not supported) j6 ref_clk ref_clk input for cs2000, cs 2100, and cs2200 sub-family devices j7 aux_out aux_out output j9 cdb2000 interface to cdb2000 (not supported) j10 usb i/o usb connector j11 c2 header for programming the micro-controller (factory use only) s1 prog dut initiates various commands (see section 4.1.3 on page 13 for details) s2 micro rst reset micro-controller s3 mode ctrl controls various board configuration aspects (see table 5 below for details) y1 - supports a dip-8 or di p-14 canned oscillator dip switch position label switch down (closed) switch up (open) 1 bnc/osc on-board osc active bnc input active 2 m0 m0 on dut driven logic ?low? m0 on dut driven logic ?high? 3 m1 m1 on dut driven logic ?low? m1 on dut driven logic ?high? 4 m2 m2 on dut driven logic ?low? m2 on dut driven logic ?high? 5 prog.msel production mode active development mode active 6 micro.msel standard operation reserved (factory use only)
ds821db1 17 cdk2000 6. cdb2000-mb schematics and layout figure 5. cdb2000-mb schematic page 1
18 ds821db1 cdk2000 figure 6. cdb2000-mb schematic page 2
cdk2000 ds821db1 19 figure 7. cdb2000-mb component map figure 8. cdb2000-mb top layer
cdk2000 20 ds821db1 figure 9. cdb2000-mb inner layer 1 - ground figure 10. cdb2000-mb inner layer 2 - power
cdk2000 ds821db1 21 figure 11. cdb2000-mb bottom layer
cdk2000 22 ds821db1 7. cdb2000-dc schematics and layout figure 12. cdb2000-dc schematics figure 13. cdb2000-dc component map
cdk2000 ds821db1 23 figure 14. cdb2000-dc top layer figure 15. cdb2000-dc inner layer 1 - ground figure 16. cdb2000-dc inner layer 2 - power figure 17. cdb2000-dc bottom layer
cdk2000 24 ds821db1 8. cdb2000-pc schematics and layout figure 18. cdb2000-pc schematics figure 19. cdb2000-pc component map
cdk2000 ds821db1 25 figure 20. cdb2000-pc top layer figure 21. cdb2000-pc inner layer 1 - ground figure 22. cdb2000-pc inner layer 2 - power figure 23. cdb2000-pc bottom layer
cdk2000 26 ds821db1 9. ordering information 10.revision history product description included hardware order # CDK2000-CLK cs2000-cp evaluation & prototyping kit 1 x cdb2000-mb 1 x cdb2000-pc-clk 1 x cdb2000-dc-clk-cp cdk-2000-clk cdk2000-lco cs2300-cp evaluation & prototyping kit 1 x cdb2000-mb 1 x cdb2000-pc-lco 1 x cdb2300-dc-lco-cp cdk-2000-lco release changes db1 initial release contacting cirrus logic support for all product questions and inquiries, c ontact a cirrus logic sales representative. to find the one nearest you, go to www.cirrus.com. important notice cirrus logic, inc. and its subsidiaries (?cirrus?) believe that the information contained in this document is accurate and reli able. however, the information is subject to change without notice and is provided ?as is? without warranty of any kind (express or implied). customers are advised to ob tain the latest version of relevant information to verify, before placing orders, that information being relied on is current and complete. all products are sold s ubject to the terms and conditions of sale supplied at the time of order acknowledgment, including those pertaining to warranty, indemnification, and limitation of liabil ity. no responsibility is assumed by cirrus for the use of this information, including use of this information as the basis for manufacture or sale of any items, or for in fringement of patents or other rights of third parties. this document is the property of cirrus and by furnishing this information, cirrus grants no license, express or impli ed under any patents, mask work rights, copyrights, trademarks, trade secrets or other intellectual property rights. cirrus owns the copyrights associated with the inf ormation contained herein and gives con- sent for copies to be made of the information only for use within your organization with respect to cirrus integrated circuits or other products of cirrus. this consent does not extend to other copying such as copying for general distribution, advertising or promotional purposes, or for creating any work for resale. certain applications usin g semiconductor products may involve potential ri sks of death, personal injury, or severe prop- erty or environmental damage (?critical applications?). cirrus products are not designed, authorized or warranted for use in products surgically implanted into the body, automotive safety or security devices, life su pport products or other crit- ical applications. inclusion of cirrus prod ucts in such applications is understood to be fully at the customer?s risk and cir- rus disclaims and makes no warranty, express, statutory or im plied, including the implied warranties of merchantability and fitness for particular purpose, with regard to any cirrus product that is used in su ch a manner. if the customer or custom- er?s customer uses or permits the use of cirrus products in critical applications, customer agrees, by such use, to fully indemnify cirrus, its officers, directors, employees, distributors and other agents from any and all liability, including at- torneys? fees and costs, that may result from or arise in connection with these uses. cirrus logic, cirrus, and the cirrus logic logo designs are trademarks of cirrus logic, inc. all other brand and product names in this document may be trademarks or service marks of their respective owners. i2c is a registered trademark of philips semiconductor. silabs is a registered trademark of silicon laboratories, inc. windows is a registered trademark of microsoft corporation. zetex is a trademark of zetex semiconductors.

▲Up To Search▲

Price & Availability of CDK2000-CLK

	To Download CDK2000-CLK Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .